Repository navigation
Conversation
Shopify CLI 4.0 removed the deprecated --force flag from `shopify app deploy`, so flyShopifyConfig aborts Dockerfile generation with "Nonexistent flag: --force" and `fly launch` fails. Use --allow-updates, the replacement Shopify recommends for non-interactive runs. Fixes fly-apps#151
MichaelDeBoey
approved these changes
Sep 19, 2026
Contributor
Author
|
Thanks for picking it up — the pre-3.90 fallback makes sense. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #151 (also reported downstream as superfly/flyctl#4944).
What
Shopify CLI 4.0 removed the deprecated
--forceflag (andSHOPIFY_FLAG_FORCE) fromshopify app deploy(4.0.0 release notes).flyShopifyConfigstill runsshopify app deploy --force --config <file>, so the CLI exits withNonexistent flag: --force, Dockerfile generation throws, andfly launchfor a Shopify app fails before writingfly.toml.Fix
Use
--allow-updates, which Shopify names as the replacement for--forcein non-interactive/CI runs (adds and updates extensions, skips the prompt, does not allow deletions). Same command is echoed in theexecutelog line.Verification
@shopify/cli@4.8.0(current latest) locally.shopify app deploy --force --config shopify.app.toml→Nonexistent flag: --force. With--allow-updatesthe flag parses and the CLI proceeds to the auth step (Authorization is required to continue), which is as far as it can go without a Shopify login.npx eslint fly.jsclean.npm test(Node 22): 114 passing, 11 failing — the same 11 fail on unmodifiedmainon this host (they shell out tobun/yarn/pnpm, which are not installed here); none touch the Shopify path.